Database management system and method which monitors activity levels and determines appropriate schedule times

ABSTRACT

A system and method for automated database management are provided. Statistics relating to operation of a database may be collected, wherein the database comprises one or more database objects. Characteristics of the database objects may be determined, either automatically or by user intervention, using the collected statistics, one or more policies, and/or one or more definitions. The policies and definitions may be defaults or may be customized by a user. Actions to be performed on the database objects may be determined, either automatically or by user intervention, based on the characteristics of the database objects. A schedule for performing the actions on the database objects may be automatically determined. The actions may be performed on the database objects based on the schedule. The actions on the database objects may be confirmed. The results of the actions on the database objects may be analyzed or monitored. Policies and/or definitions may be reconfigured based on the results. The system and method may automatically decide to perform one or more REORG actions on the database objects based on the statistics. A recommendation of a modification to one or more of the database objects may be generated based on the statistics. The scheduled actions may be modified as a result of detecting a change in the characteristics or usage of at least one of the database objects.

PRIORITY CLAIM

This application claims the benefit of U.S. Provisional Application No.60/252,873 entitled “AUTOMATED DATABASE MANAGEMENT SYSTEM AND METHOD,”filed Nov. 22, 2000.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to computer systems and software. Moreparticularly, the invention relates to management of database systems.2. Description of the Related Art The data processing resources ofbusiness organizations are increasingly relying on database managementsystems (DBMS) such as relational database management systems (RDBMS)for their data storage and processing needs. One example of such anRDBMS is “DB2” from International Business Machines. Rapid data growthand the growing complexity of business applications have made the DBMSeven more critical to its users than in the past. As a result,organizations that rely on these systems often expect round-the-clock,“24×7” availability as well as nearly instant solutions to the oftenthorny problems that may arise. Consequently, these organizations needcapable DBMS administrators who are able to tackle the problems and getthe most out of the DBMS.

The maintenance and management of a DBMS is often complex and fraughtwith difficulty, especially for organizations with weighty and complexdata management needs. Typically, competent DBMS administration requirestraining and knowledge in the often arcane and esoteric details ofcommercial products such as DB2, DB2 management tools, and countlessother DBMS solutions, tools, and utilities. DBMS maintenance andmanagement also typically requires manual intervention by a skilledadministrator to conduct various DBMS management tasks. As the demandfor DBMS solutions increases, however, the supply of capable DBMSadministrators has not increased accordingly. Therefore, manyorganizations that rely on DBMS solutions for their business needs areunderstaffed at this critical position.

One approach towards this problem might include automating variouselements of database administration so that the process demands lessskill on an administrator's behalf. Such a solution might also includemanagement tools that can be used “out of the box” and with minimalconfiguration. The solution might assist the user in combating commonproblems such as tablespace growth, storage fragmentation, page splits,changes in the data distribution (cardinality), changes in the clusterratio, free space, and hot spots.

Therefore, it is desirable to provide an improved system and method fordatabase management.

SUMMARY OF THE INVENTION

The present invention provides various embodiments of a method andsystem for automated database management. Various embodiments of thesystem and method for automated database management may be referred toherein as an “Object Advisor.” The Object Advisor may identifyconditions that cause performance or availability problems in data baseobjects. It may then plan, execute, and manage maintenance activities tocorrect those conditions. Object Advisor may also prioritize themaintenance tasks and optimizes utility parameters and maintenanceprocessing to ensure that the customers' resources are used in the mosteffective way possible while ensuring that the most critical problemsare addressed first.

One embodiment may provide a database management system and method whichcollects statistics and automatically determines and schedulesappropriate actions based on the statistics. In one embodiment,statistics relating to operation of a database may be collected, whereinthe database comprises one or more database objects. The statistics mayinclude, for example, object-level statistics and/or activity-levelstatistics. Characteristics of the database objects may be automaticallydetermined. In one embodiment, automatically determining characteristicsof the database objects may include automatically determiningcharacteristics of the database objects using the collected statistics,one or more policies, and/or one or more definitions. The policies anddefinitions may be defaults or may be customized by a user. Actions tobe performed on the database objects may be automatically determinedbased on the automatically determined characteristics of the databaseobjects. A schedule for performing the actions on the database objectsmay be automatically determined. In one embodiment, the actions may beperformed on the database objects based on the schedule. The performingthe actions on the database objects may be confirmed. The results of theactions on the database objects may be analyzed or monitored. Policiesand/or definitions may be reconfigured based on the analyzing theresults of the performing the scheduled actions on the database objects.

One embodiment may provide a database management system and method whichautomatically schedules and performs actions and monitors results. Inone embodiment, statistics relating to operation of a database may becollected, wherein the database comprises one or more database objects.Characteristics of the database objects may be determined eitherautomatically or by intervention of a user. Actions to be performed onthe database objects may be determined, either automatically or byintervention of a user, based on the characteristics of the databaseobjects. A schedule for performing the actions on the database objectsmay be automatically determined. In one embodiment, the actions may beperformed on the database objects based on the schedule. The performingthe actions on the database objects may be confirmed. The results of theactions on the database objects may be analyzed or monitored. Policiesand/or definitions may be reconfigured based on the analyzing theresults of the performing the scheduled actions on the database objects.

One embodiment may provide a database management system and method whichmonitors activity levels and determines appropriate schedule times. Inone embodiment, statistics relating to operation of a database may becollected, wherein the database comprises one or more database objects.The statistics may include, for example, object-level statistics and/oractivity-level statistics. The activity-level statistics may measure alevel of activity or usage of the one or more database objects.Characteristics of the database objects may be determined eitherautomatically or by intervention of a user. Actions to be performed onthe database objects may be determined, either automatically or byintervention of a user, based on the characteristics of the databaseobjects. A schedule for performing the actions on the database objectsmay be automatically determined based on the activity-level statistics.In one embodiment, the actions may be performed on the database objectsbased on the schedule. The performing the actions on the databaseobjects may be confirmed. The results of the actions on the databaseobjects may be analyzed or monitored.

One embodiment may provide a database management system and method whichmonitors action results and adjusts user parameters in response. In oneembodiment, actions to be performed on the database objects may bedetermined, either automatically or by intervention of a user, based onthe characteristics of database objects, wherein a database comprisesone or more database objects. The actions may be performed on thedatabase objects based on the schedule. The results of the actions onthe database objects may be analyzed or monitored. One or more policiesor definitions may be reconfigured based on the monitoring the resultsof the performing the actions on the database objects.

One embodiment may provide a database management system and method whichdetermines space efficiency of objects and initiates databasereorganizations. In one embodiment, statistics relating to operation ofa database may be collected, wherein the database comprises one or moredatabase objects, and wherein the statistics comprise statisticsregarding use of storage space by the database objects. The system andmethod may automatically decide to perform one or more REORG actions onthe database objects based on the statistics. A REORG engine may beinstructed to perform the REORG actions.

One embodiment may provide a database management system and method whichrecommends changes in physical characteristics of objects and partitionchanges. In one embodiment, statistics relating to operation of adatabase may be collected, wherein the database comprises one or moredatabase objects. A recommendation of a modification to one or more ofthe database objects may be generated based on the statistics. Themodification may include, for example, a new partition, a new key, or aanother physical change to one of the database objects. The recommendedmodification may be performed on one or more of the database objects.

One embodiment may provide a database management system and method whichincludes adaptive management of database objects. In one embodiment,statistics relating to operation of a database may be collected, whereinthe database comprises one or more database objects. Characteristics andusage of the database objects may be determined. Actions to be performedon the database objects may be determined based on the characteristicsof the database objects. A schedule for performing the actions on thedatabase objects may be determined based on the usage of the databaseobjects. A change may be detected in the characteristics or usage of atleast one of the database objects. The scheduled actions may be modifiedas a result of the change in the characteristics or usage of at leastone of the database objects.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the invention will become apparent uponreading the following detailed description and upon reference to theaccompanying drawings in which:

FIG. 1 illustrates a computer system which is suitable for implementinga database management system and method according to severalembodiments;

FIG. 2 is a block diagram of the computer system of FIG. 1 which issuitable for implementing a database management system and methodaccording to several embodiments;

FIG. 3 illustrates an enterprise computing environment which is suitablefor implementing a database management system and method according toseveral embodiments;

FIG. 4 illustrates a method for database management according to theprior art;

FIG. 5 illustrates a method for automated and intelligent databasemanagement according to several embodiments;

FIG. 6 illustrates an architecture for a system for automated andintelligent database management according to several embodiments;

FIGS. 7 a and 7 b are flowcharts illustrating an automated andintelligent database management method according to several embodiments;

FIG. 8 is a flowchart illustrating a database management system andmethod which collects statistics and automatically determines andschedules appropriate actions based on the statistics according to oneembodiment;

FIG. 9 is a flowchart illustrating a database management system andmethod which automatically schedules and performs actions and monitorsresults according to one embodiment;

FIG. 10 is a flowchart illustrating a database management system andmethod which monitors activity levels and determines appropriateschedule times according to one embodiment;

FIG. 11 is a flowchart illustrating a database management system andmethod which monitors action results and adjusts user parameters inresponse according to one embodiment;

FIG. 12 is a flowchart illustrating a database management system andmethod which determines space efficiency of objects and initiatesdatabase reorganizations according to one embodiment;

FIG. 13 is a flowchart illustrating a database management system andmethod which recommends changes in physical characteristics of objectsand in partitions according to one embodiment; and

FIG. 14 is a flowchart illustrating a database management system andmethod which performs adaptive management of database objects accordingto one embodiment.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that the drawings and detaileddescription thereto are not intended to limit the invention to theparticular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents, and alternatives falling withinthe spirit and scope of the present invention as defined by the appendedclaims.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1—A Typical Computer System

FIG. 1 illustrates a typical, general-purpose computer system 100 whichis suitable for implementing a database management system and methodaccording to one embodiment. The computer system 100 typically comprisescomponents such as computing hardware 102, a display device such as amonitor 104, an alphanumeric input device such as a keyboard 106, andoptionally an input device such as a mouse 108. The computer system 100is operable to execute computer programs which may be stored on disks110 or in computing hardware 102. In various embodiments, the computersystem 100 may comprise a desktop computer, a laptop computer, a palmtopcomputer, a network computer, a personal digital assistant (PDA), anembedded device, a smart phone, or any other suitable computing device.

FIG. 2—Computing Hardware of a Typical Computer System

FIG. 2 is a block diagram illustrating the computing hardware 102 of atypical, general-purpose computer system 100 which is suitable forimplementing a database management system and method according to oneembodiment. The computing hardware 102 includes at least one centralprocessing unit (CPU) or other processor(s) 122. The CPU 122 isconfigured to execute program instructions which implement the improvedmanagement console as described herein. The CPU 122 is preferablycoupled to a memory medium 124.

As used herein, the term “memory medium” includes a non-volatile medium,e.g., a magnetic medium, hard disk, or optical storage; a volatilemedium, such as computer system memory, e.g., random access memory (RAM)such as DRAM, SDRAM, SRAM, EDO RAM, Rambus RAM, etc.; or an installationmedium, such as CD-ROM, floppy disks, or a removable disk, on whichcomputer programs are stored for loading into the computer system. Theterm “memory medium” may also include other types of memory. The memorymedium 124 may therefore store program instructions and/or data whichimplement the database management system and method as described herein.Furthermore, the memory medium 124 may be utilized to install theprogram instructions and/or data. In a further embodiment, the memorymedium 124 may be comprised in a second computer system which is coupledto the computer system 100 through a network 128. In this instance, thesecond computer system may operate to provide the program instructionsstored in the memory medium 124 through the network 128 to the computersystem 100 for execution.

The CPU 122 may also be coupled through an input/output bus 120 to oneor more input/output devices that may include, but are not limited to, adisplay device such as a monitor 104, a pointing device such as a mouse108, a keyboard 106, a track ball, a microphone, a touch-sensitivedisplay, a magnetic or paper tape reader, a tablet, a stylus, a voicerecognizer, a handwriting recognizer, a printer, a plotter, a scanner,and any other devices for input and/or output. The computer system 100may acquire program instructions and/or data for implementing thedatabase management system and method as described herein through theinput/output bus 120.

The CPU 122 may include a network interface device 128 for coupling to anetwork. The network may be representative of various types of possiblenetworks: for example, a local area network (LAN), wide area network(WAN), or the Internet. The improved management console as describedherein may therefore be implemented on a plurality of heterogeneous orhomogeneous networked computer systems such as computer system 100through one or more networks. Each computer system 100 may acquireprogram instructions and/or data for implementing the databasemanagement system and method as described herein over the network.

FIG. 3—A Typical Enterprise Computing Environment

FIG. 3 illustrates an enterprise computing environment 200 according toone embodiment. An enterprise 200 comprises a plurality of computersystems such as computer system 100 which are interconnected through oneor more networks. Although one particular embodiment is shown in FIG. 3,the enterprise 200 may comprise a variety of heterogeneous computersystems and networks which are interconnected in a variety of ways andwhich run a variety of software applications.

One or more local area networks (LANs) 204 may be included in theenterprise 200. A LAN 204 is a network that spans a relatively smallarea. Typically, a LAN 204 is confined to a single building or group ofbuildings. Each node (i.e., individual computer system or device) on aLAN 204 preferably has its own CPU with which it executes computerprograms, and often each node is also able to access data and devicesanywhere on the LAN 204. The LAN 204 thus allows many users to sharedevices (e.g., printers) as well as data stored on file servers. The LAN204 may be characterized by any of a variety of types of topology (i.e.,the geometric arrangement of devices on the network), of protocols(i.e., the rules and encoding specifications for sending data, andwhether the network uses a peer-to-peer or client/server architecture),and of media (e.g., twisted-pair wire, coaxial cables, fiber opticcables, radio waves). FIG. 3 illustrates an enterprise 200 including oneLAN 204. However, the enterprise 200 may include a plurality of LANs 204which are coupled to one another through a wide area network (WAN) 202.A WAN 202 is a network that spans a relatively large geographical area.

Each LAN 204 comprises a plurality of interconnected computer systems orat least one computer system and at least one other device. Computersystems and devices which may be interconnected through the LAN 204 mayinclude, for example, one or more of a workstation 210 a, a personalcomputer 212 a, a laptop or notebook computer system 214, a servercomputer system 216, or a network printer 218. An example LAN 204illustrated in FIG. 3 comprises one of each of these computer systems210 a, 212 a, 214, and 216 and one printer 218. Each of the computersystems 210 a, 212 a, 214, and 216 is preferably an example of thetypical computer system 100 as illustrated in FIGS. 1 and 2. The LAN 204may be coupled to other computer systems and/or other devices and/orother LANs 204 through a WAN 202.

A mainframe computer system 220 may optionally be coupled to theenterprise 200. As shown in FIG. 3, the mainframe 220 is coupled to theenterprise 200 through the WAN 202, but alternatively the mainframe 220may be coupled to the enterprise 200 through a LAN 204. As shown in FIG.3, the mainframe 220 is coupled to a storage device or file server 224and mainframe terminals 222 a, 222 b, and 222 c. The mainframe terminals222 a, 222 b, and 222 c access data stored in the storage device or fileserver 224 coupled to or comprised in the mainframe computer system 220.

The enterprise 200 may also comprise one or more computer systems whichare connected to the enterprise 200 through the WAN 202: as illustrated,a workstation 210 b and a personal computer 212 b. In other words, theenterprise 200 may optionally include one or more computer systems whichare not coupled to the enterprise 200 through a LAN 204. For example,the enterprise 200 may include computer systems which are geographicallyremote and connected to the enterprise 200 through the Internet.

FIG. 4—A Database Management Method from the Prior Art

FIG. 4 illustrates a method for database management according to theprior art. This prior art method requires substantial manualintervention by a user such as a highly skilled database administrator.In 402, the user manually initiates the gathering of information aboutobjectives. Objectives may relate to computer system resource usageparameters such as CPU time, “real-world” time, and storage utilization,for example. In 404, the information is gathered using the prior artdatabase management software.

In 406, the information is analyzed, typically by the prior art databasemanagement software. The software may generate recommendations based onthe analysis. In 408, jobs and/or reports may be generated by the priorart database management software based on the analysis.

In 410, the user may manually apply the recommended actions to improvethe performance of the DBMS or otherwise meet the desired objectives.

FIG. 5—An Automated and Intelligent Database Management Method

FIG. 5 illustrates a method for automated and intelligent databasemanagement according to several embodiments. A computer systemarchitecture for performing this method is described with reference toFIG. 6. Various embodiments of the system and method for automateddatabase management may be referred to herein as an “Object Advisor.”Various of these embodiments of the Object Advisor and its componentsare described in more detail as follows. The Object Advisor Solution Setmay identify conditions that cause performance or availability problemsin data base objects. It may then plan, execute, and manage maintenanceactivities to correct those conditions. Object Advisor may alsoprioritize the maintenance tasks and optimizes utility parameters andmaintenance processing to ensure that the customers' resources are usedin the most effective way possible while ensuring that the most criticalproblems are addressed first.

In 502, database objects and their attributes may be configured. In oneembodiment, the configuration may include setting default values (e.g.,resource usage thresholds for generating alerts) upon installation ofthe database management software. The use of defaults may reduce thelevel of skill necessary for the user.

In 504, database activities are monitored, and information aboutdatabase objects and their attributes may be gathered by the databasemanagement software.

In 506, database objects and their attributes may be analyzed by thedatabase management software.

In 508, it may be determined whether deterministic characteristicsshould be gathered. If so, then in 510 attributes of database objectsmay be collected, and in 512 the attributes and activities may becorrelated.

In 514, a rule-based engine may be applied to the analyzed information(including the correlated attributes and activities, if applicable).

In 516, heuristic threshold analysis may be performed.

In 518, it may be determined whether thresholds should be modified. Ifso, then in 520 the knowledge base may be reconfigured with the modifiedthresholds.

In 522, any actions such as recommendations may be performed on thedatabase objects or other relevant subsystems.

FIG. 6—An Automated and Intelligent Database Management Architecture

FIG. 6 illustrates an architecture for a system for automated andintelligent database management according to several embodiments. Invarious embodiments, the Object Advisor may be executable in whole orpart on a mainframe computer system 220. Throughout the followingdescription, DB2 is used as an example of one DBMS to which ObjectAdvisor may be applied; in other embodiments, Object Advisor may beexecutable to manage other database management systems.

In one embodiment, there are four general categories of componentscontained in the Object Advisor solution set: Data CollectionComponents, Decision Making Components, Execution Management Components,User Interface and Configuration Components. In one embodiment, theObject Advisor components are designed in a modular manner to enablethem to be packaged in various ways to solve related problems in othersolution sets as well. For example, the Object Advisor solution set maysolve the problem of managing the desired state of Database objects.When the Data Collection, Decision Making, and Configuration componentsfrom Object Advisor are employed together, an organization may have theability to determine object-related causes of general performanceproblems such as application response time has slowed. Adding the ObjectAdvisor Execution components may enable an organization not only tocorrect the problem, but also to verify that the actions taken actuallymade a difference in the performance of that same application.

Data Collection Components

In one embodiment, the Data Collection components may utilize high-speedcollection techniques to gather information about database objects suchas Database objects. This information describes the physical aspects ofdatabase objects and how the data within those objects is utilized.Object Advisor may use the collected data for decision-making andreporting purposes. The object usage data collector 602 may be used fordata collection.

Object Usage Monitor and Analysis

In one embodiment, the object usage monitor 604 may execute continuallyand track information about how specific database objects are used.Information about the type of activities that occur, how frequently theyoccur, and when they occur is collected and saved. The usage monitor may604 also identify the type of access that is used to retrieve data fromspecific datasets. The usage monitor may log the collected informationto an OA (Object Advisor) data usage statistics table 636. The objectusage analysis component 606 may be used to correlate the usage datarelative to object-level performance metrics. Potential problems may belogged to an events table 630. Correlation may provide targeted analysisallowing for a proactive, efficient solution that is scalable to verylarge environments.

Object Statistics Collector

An object statistics collector such as BMCSTATS 610, available from BMCSoftware, Inc., may collect detailed statistical information aboutdatabase objects. The collection can be zoomed in to specific types ofstatistics and can be collected in a real-time manner or as a part of ascheduled process. The statistical information collected by thiscomponent 610 describes the physical characteristics of database objectsand is saved for historical and analytical purposes in the ObjectAdvisor repository tables such as object statistics table 640. In oneembodiment, the most common data provided by the object statisticscollector 610 includes space and access-path statistics that can beplaced in the DB2 catalog in lieu of RUNSTATS data. The data provided bythis component may enable Object Advisor to determine whetherperformance or availability problems exist on specific database objects.It may enable the pinpointing of which objects require attention and howurgently that attention is required.

Problem Determination Components

The problem determination components, including problem determinationcomponent 608, may evaluate information about the usage of databaseobjects for indications of potential performance or availabilityconcerns. When concerns are identified, detailed statistics may berequested and analyzed to determine whether an actual problem exists andwhat actions would be required to correct it.

Problem Determination

The problem determination component 608 may analyze object usage andstatistical information looking for performance, availability, or otherobject related problems that could impact the use of database objectdata. The problem determination component may use information fromtables such as the events table 630 and a DBMS (such as DB2) catalogtable 632. The event analysis component 612 may provide similarfunctionality for events. Information describing any problem that isfound and the object it affects, and the remedy required to correct thesituation, may be logged in the repository tables and/or files 638. Thisdata may also be consumed by the action determination components. Theproblem determination component 608 may isolate performance andavailability problems and identify the appropriate reaction by drawingon an established knowledge base. The decision-making capabilitiesprovided in this component 608 may reduce the level of experiencerequired by the user.

Threshold Adjustment

The product tuning analysis component 618 may manage and automaticallyadjust the thresholds used to monitor data usage and the thresholds usedin problem determination. This component may use information from ObjectAdvisor repository tables such as a maintenance history table 652, forexample. This component may enable the Object Advisor to tweakthresholds as needed to ensure the effectiveness of the problemdetermination components. The ability to govern its own thresholds mayenable Object Advisor to identify problems at the appropriate time andseverity. Therefore, as database objects or applications change, usersmay not need to reconfigure Object Advisor. The decision-makingcapability provided in this component may reduce the level of experiencerequired by the user. In one embodiment, thresholds and otherconfiguration settings may be manually tuned by a user with the manualproduct configuration and tuning component 616.

Action Determination Components

When a condition is identified by the problem determination component orother piece of software, the Action Determination components mayidentify the corresponding action for the condition. The identifiedactions may then be used to construct, prioritize, and optimize aworkload that can be built and managed by the execution managementcomponents.

Action Determination

The action determination component 614 may analyze the remedyrecommended during problem determination and identify the variousutilities, commands, and/or programs that perform that service. It maythen determine the most effective action for correcting the problem andwhether any additional actions should be performed to prevent new orassociated problems from occurring. The action determination componentmay also construct the corresponding maintenance workload(s) in workloadtable 644 and assign priorities to individual units of work based on theseverity of the underlying object condition. The action determinationcomponent may use information from tables such as a service requeststable 634. The data provided by this component 614 may be consumed bythe workload optimization components.

The ability to automatically determine the most effective approach tocorrecting a problem and to identify the objects most in need of repairmay reduce human interaction. This capability may be especiallyimportant in large enterprises. The decision-making capability providedin this component 614 may reduce the level of experience required by theuser.

Workload Optimizer

The workload analysis component 626 may analyze the DBMS batch workloadand modify it as needed for efficiency. In one embodiment, utilityoptions are tuned, duplicate tasks are identified, grouping andparallelism options are analyzed, and dependencies within the unit ofwork are noted. The workload is then modified as needed before it isregistered with the scheduling component 624. Optimizing the workloadmay reduce the elapsed time of maintenance tasks while maximizing systemresources. This may be especially important in large enterprises. Thedecision-making capability provided in this component may reduce thelevel of experience required by the user.

Execution Management Components

The Execution Management Components may build, manage and execute therequested workload, thereby ensuring that customer resources are usedeffectively and that maximum throughput is achieved. The componentsdescribed below may be included in this area of the Object Advisor.

Workload Preparation

The workload monitor component 622 may use the information provided bythe workload analysis component 626 and the resource estimationcomponent to register work to the scheduler 624. It may convert theworkload into jobs and describe resource constraints, dependencies,priorities, and window constraints to the scheduling component. Theworkload monitor component 622 may automate the registry of complexdependencies and resource requirements, thereby enabling the workload tobe automatically managed for the user.

Resource Estimation

These components (not shown) may estimate the resources that will berequired for each specific task in the maintenance workload. Estimatedelapsed time may be calculated, and dataset sizes and devicerequirements are calculated for storage devices. This information may beconsumed by the workload monitor component 622 when registering work tothe scheduler 624. Performing resource estimation may reduce the levelof experience required by the user and ensure the reliable execution ofmaintenance tasks.

JCL Generation

The JCL 628 generation component (not shown) may be used to create theJCL and jobs required to execute the workload. This may includesingle-step worklist format jobs, traditional JCL to be managed by theuser, and JCL that can be managed by a scheduling component 624.Automating the creation of JCL 628 may reduce the level of experiencerequired by the user and ensure the reliable execution of maintenancetasks.

Scheduling Component

The scheduling component 624, such as Control-M available from BMCSoftware, Inc., may manage the entire workload. This component mayconsider priorities, resource requirements, resource availability, anddependencies while determining which tasks to initiate. The schedulingcomponent may initiate multiple tasks in parallel (within and across thesysplex) as determined by dependency and resource requirements. Thiscomponent may automatically manage maintenance tasks within a batchwindow, thereby optimizing system resource usage and maximizingthroughput.

Execution

The execution component (not shown) may enable the Object Advisor toautomate error handling, to ensure that objects are left in a usablestate, and to invoke the appropriate utility or command program. Thiscomponent may also capture information regarding the resources consumed,return codes, and elapsed time of the utility. This information may berelated to the object being operated on and logged into the repositorytables 646. Automated error handling may ensure the availability ofcritical applications.

Status Handling and Reporting

This component (not shown) may monitor the completion of tasks andperform cleanup processing in the repository tables 646. Tasks may bemarked as complete, tasks that are not required may be identified, datausage counters may be reset as needed, and information may be loggedinto the history tables. This component may also identify objects thatneed to be incorporated into end of the window jobs based on work thatcompletes successfully. The ability to report task status andconsolidate specific work into end of the window jobs may reduce theelapsed time of maintenance tasks while maximizing system resources.

User Interface and Product Configuration Components

The User Interface may provide an interactive method of driving andcustomizing the solution set. It may enable the user to view, modify andsave predefined options, default values, and rules. These components mayalso enable users to create their own options, defaults, and rules. Inone embodiment, the data managed within the configuration components maybe employed by other Object Advisor components to determine how variousobjects and actions should be managed. Specific configuration componentsmay be described below.

Application Definition

This component (not shown) may provide a facility for logically groupingdatabase objects together. A definition may include a set of ruleswhich, when applied to the DBMS catalog, results in a list of Databaseobjects. The rules that define the logical grouping of objects may begiven a name (e.g., the application name) and stored in the ObjectAdvisor Repository 646. Object Advisor may use Application Definitionsto implement policies regarding Utility Automation.

Utility Specification and Generation

This component (not shown) may provide a facility for registeringutilities, commands, or programs and for specifying how specific actionsshould be executed. Utility programs and commands may be automaticallyregistered with the Object Advisor at installation time. Through thisfacility, users may also register other executable programs, therebyenabling them to be invoked within an ad-hoc job stream, or as a part ofthe automation process.

Task Configuration

The Task configuration component (not shown) may provide a facility forcoupling multiple utilities, commands, or programs into a single unit ofwork. Options related to how the specific utilities in the task listshould be initiated may also be defined in the task configurationcomponents. These options may include parallelism, grouping, andconditional execution options for the various utilities in the list. TheObject Advisor decision-making components may use the task relateddefinitions to determine how to construct job streams when correctingspecific performance problems.

Policy Definition Editors

The policy definition editors (not shown) may provide facilities fordefining and implementing policies. As used herein, the term “policies”include rules that may govern how objects and actions are managed bycomponents. Policies may be established for all decisions made withinthe solution set. They may be specialized towards DBMS object andmaintenance management and instruct the product regarding what to do,when to do it, and how to do it.

Scheduling Resource Definition

The scheduling resource definition components (not shown) may provide ameans of specifying limits to the resources, such as tape devices, thatmay be used when executing maintenance tasks. This component may alsoenable the customer to indicate windows in which specific utilities mayexecute or windows in which specific objects may or may not be operatedon. The data managed by the scheduling resource definition componentsmay be used to register workload requirements to the ExecutionComponents.

Statistics Management

The statistics management components (not shown) may facilitate themigration, cleanup, and summarization of historical statistics data.Detailed object and data usage statistics may be summarized, orconsolidated, into specific time intervals, thereby allowing thecustomer to maintain a longer history of information without the spacerequirements associated with detailed historical data. Old or outdatedinformation may also be purged from the repository tables. In addition,these components may facilitate the migration of object statistics fromone subsystem to another as well as enabling migration between therepository tables and the DBMS catalog. Managing statistics for the usermay ensure that accurate sets of statistical data are available fordecision-making and reporting purposes. The migration of catalogstatistics may enable users to automatically simulate productionenvironments in test systems.

Predefined Policies and Configuration

In one embodiment, Object Advisor may be installed with a complete setof definitions and policies that may constitute “best-practice”techniques regarding DBMS object maintenance. These definitions andpolicies may be stored in a knowledge base 642. The user may view orcustomize these policies and definitions as needed to meet shopstandards or individual requirements. The user may also create newpolicies and/or definitions as needed. The knowledge provided in thesedefinitions may reduce the level of experience required by the user.

Catalog Browser

This component (not shown) may provide an ad-hoc means for a user tointeractively display lists of database objects. One or more objects ona list may be selected and used to launch an Object Advisor task oraction. It may also facilitate the object to action approach for theuser interface. This functionality may enable the user to access ObjectAdvisor configuration data more efficiently.

Space Estimation

This component (not shown) may provide an ad-hoc means for a user tointeractively determine the space required for database objects. Thisfunctionality may enable users to precisely calculate storagerequirements for database objects.

Graphing, Reporting, and Trend Analysis

This set of visualization and data management components 620 may enablethe detailed and historical data usage statistics and object statisticsto be viewed in a meaningful way. Various graphs and reports may beprovided to highlight problems and trends regarding the performance andusage of database objects. Reports 648 and graphs 650 may provide acommunication vehicle for complex numerical data.

Object Optimization Solutions Based on Object Advisor Technology

The components, architectures, methods, and systems discussed above mayprovide the basis for other object-related performance solutions. In oneembodiment, the previously discussed solution set may be focused onmanaging the desired state of database objects by watching for problemsand correcting them. Additional Object Optimization solutions mayproactively search for changes that can be made to improve theperformance of database objects. The following are some of thecomponents that may be included in various embodiments of theOptimization Solution.

Partition Advisor

Object Advisor's Optimization Solution may identify object partitionsthat are approaching a maximum data set size. To ensure thatapplications will be able to continue processing, it is recommended thatthe data in the full partition be spread across multiple partitions.Object Advisor may analyze the number and size of existing partitionsand determine whether to spread the data across existing datasets orwhether a new dataset should be created to hold a portion of the data.Column distribution statistics may also be analyzed to calculate a newkey range for the data. Object Advisor may also identify partitions thatare accessed more heavily or contain significantly more data thanothers. When this occurs, the partitions may be analyzed to determinethe best method of balancing the data among the partitions.

Dataset Placement Advisor

Object Advisor's Optimization Solution may identify datasets that shouldnot be located on the same DASD volumes. These datasets may bephysically related, logically related, or otherwise heavily accesseddatasets. Information may be recorded in the Object Advisor repositoryto indicate where specific dataset should or should not be placed. Thisinformation may be recorded and used when datasets are redefined duringREORG or other processes. In one embodiment, object Advisor may alsorelocate datasets that are currently in contention on a DASD device.

Free Space Advisor

Object Advisor's Optimization Solution may identify hotspots (aclustering of insert/update activity) in data objects that aredisorganized. This information may be passed to a REORG utility, therebyenabling it to place the free space more effectively. In one embodiment,Object Advisor may monitor objects to determine whether they are beingreorganized too frequently. When this occurs, trend analysis may beperformed to calculate new free space values that will lessen thefrequency of REORG operations. In addition, new space allocation valuesmay be calculated taking the modified free space into account. Aworkload script may then be written to redefine and reorganize thedatasets.

Compression Advisor

The Compression Analysis component of the Object Advisor OptimizationSolution may determine the effectiveness of existing data compression.If not enough compression is received, or processing costs are too high,compression may be turned off. In addition, Object Advisor may analyzestatistical column information and recommend or enable compression forobjects that would benefit. Object Advisor may then determine the mosteffective compression algorithm for specific objects based on the datacontained in the database and how it is used.

FIG. 7—An Automated and Intelligent Database Management Method

FIGS. 7 a and 7 b are flowcharts illustrating an automated andintelligent database management method according to several embodiments.FIG. 7 a illustrates an analysis phase of the database managementmethod.

In 702, the DBMS may be monitored and analyzed as discussed withreference to FIG. 6.

In 704, problems with database objects (e.g., DB2 objects) may beidentified. In 706, if it is determined that there is not enoughinformation to determine conclusively whether a problem exists, thenproceed to 708 for collection of statistics. If it is determined in 710that there are no problems with database objects, then thresholds areanalyzed and adjusted in 712, and object usage is again monitored in702.

In 714, determine the services needed to satisfy the problem. In 716,determine whether the service request creates additional problems. Ifso, return to 704 for problem identification. If not, then report thecondition and potential resolution to the user in 720 by generating areport 722.

In 724, determine if the user wants to fix the problem(s) as outlined inthe report 722. If so, proceed to 752 of FIG. 7 b. If not, return to 702and continue to monitor the database objects.

FIG. 7 b illustrates a execution phase of the database managementmethod. In 752, determine the tasks needed to perform the recommendedservices. In 754, determine if redundant tasks have been identified, andif not, identify a preferred task for each set of redundant tasks in756.

In 758, build an executable workload and generate a workload report 760and suitable JCL 628. In 762, determine if the Object Advisor is tomanage the work. If not, proceed to 702 of FIG. 7 a and continue tomonitor the database objects. If so, schedule the workload in 764. In766, submit and control the jobs in the workload. In 768, monitor theworkload.

FIGS. 8 Through 14—Various Database Management Methods

FIGS. 8 through 14 illustrate various database management methodsaccording to various embodiments of the invention.

FIG. 8 is a flowchart illustrating a database management system andmethod which collects statistics and automatically determines andschedules appropriate actions based on the statistics according to oneembodiment. In one embodiment, statistics relating to operation of adatabase may be collected, wherein the database comprises one or moredatabase objects, in 802. The statistics may include, for example,object-level statistics and/or activity-level statistics. In 804,characteristics of the database objects may be automatically determined.In one embodiment, automatically determining characteristics of thedatabase objects may include automatically determining characteristicsof the database objects using the collected statistics, one or morepolicies, and/or one or more definitions. The policies and definitionsmay be defaults or may be customized by a user. In 806, actions to beperformed on the database objects may be automatically determined basedon the automatically determined characteristics of the database objects.A schedule for performing the actions on the database objects may beautomatically determined in 808. In one embodiment, in 810, the actionsmay be performed on the database objects based on the schedule. Theperforming the actions on the database objects may be confirmed. Theresults of the actions on the database objects may be analyzed ormonitored. In one embodiment, policies and/or definitions may bereconfigured based on the analyzing the results of the performing thescheduled actions on the database objects.

FIG. 9 is a flowchart illustrating a database management system andmethod which automatically schedules and performs actions and monitorsresults according to one embodiment. In one embodiment, in 812,statistics relating to operation of a database may be collected, whereinthe database comprises one or more database objects. Characteristics ofthe database objects may be determined either automatically or byintervention of a user in 814. Actions to be performed on the databaseobjects may be determined, either automatically or by intervention of auser, based on the characteristics of the database objects in 816. Aschedule for performing the actions on the database objects may beautomatically determined in 818. In one embodiment, the actions may beperformed on the database objects based on the schedule in 820. Theperforming the actions on the database objects may be confirmed in 822.In 824, in one embodiment, the results of the actions on the databaseobjects may be analyzed or monitored. In one embodiment, policies and/ordefinitions may be reconfigured based on the analyzing the results ofthe performing the scheduled actions on the database objects.

FIG. 10 is a flowchart illustrating a database management system andmethod which monitors activity levels and determines appropriateschedule times according to one embodiment. In one embodiment,statistics relating to operation of a database may be collected, whereinthe database comprises one or more database objects, in 832. Thestatistics may include, for example, activity-level statistics. Theactivity-level statistics may measure a level of activity or usage ofthe one or more database objects. In 834, characteristics of thedatabase objects may be determined either automatically or byintervention of a user. In 836, actions to be performed on the databaseobjects may be determined, either automatically or by intervention of auser, based on the characteristics of the database objects. In 838, aschedule for performing the actions on the database objects may beautomatically determined based on the activity-level statistics. In oneembodiment, the actions may be performed on the database objects basedon the schedule in 840. In 842, the performing the actions on thedatabase objects may be confirmed. The results of the actions on thedatabase objects may be analyzed or monitored in 844.

FIG. 11 is a flowchart illustrating a database management system andmethod which monitors action results and adjusts user parameters inresponse according to one embodiment. In one embodiment, in 852,statistics relating to operation of a database may be collected, whereinthe database comprises one or more database objects. In 854,characteristics of the database objects may be determined eitherautomatically or by intervention of a user. In 856, actions to beperformed on the database objects may be determined, eitherautomatically or by intervention of a user, based on the characteristicsof database objects. The actions may be performed on the databaseobjects based on the schedule in 858. In 860, the results of the actionson the database objects may be analyzed or monitored. One or morepolicies or definitions may be reconfigured based on the monitoring theresults of the performing the actions on the database objects in 862.

FIG. 12 is a flowchart illustrating a database management system andmethod which determines space efficiency of objects and initiatesdatabase reorganizations according to one embodiment. In one embodiment,in 872, statistics relating to operation of a database may be collected,wherein the database comprises one or more database objects, and whereinthe statistics comprise statistics regarding use of storage space by thedatabase objects. The system and method may automatically decide toperform one or more REORG actions on the database objects based on thestatistics in 874. In 876, a REORG engine may be instructed to performthe REORG actions.

FIG. 13 is a flowchart illustrating a database management system andmethod which recommends changes in physical characteristics of objectsand in partitions according to one embodiment. In one embodiment,statistics relating to operation of a database may be collected, whereinthe database comprises one or more database objects, in 882. Arecommendation of a modification to one or more of the database objectsmay be generated based on the statistics in 884. The modification mayinclude, for example, a new partition, a new key, or a another physicalchange to one of the database objects. The recommended modification maythen be performed on one or more of the database objects.

FIG. 14 is a flowchart illustrating a database management system andmethod which performs adaptive management of database objects accordingto one embodiment. In one embodiment, statistics relating to operationof a database may be collected, wherein the database comprises one ormore database objects, in 886. Characteristics and usage of the databaseobjects may be determined in 888 and 890. In 892, actions to beperformed on the database objects may be determined based on thecharacteristics of the database objects. In 894, a schedule forperforming the actions on the database objects may be determined basedon the usage of the database objects. In 896, a change may be detectedin the characteristics or usage of at least one of the database objects.The scheduled actions may be modified as a result of the change in thecharacteristics or usage of at least one of the database objects in 898.

Various embodiments further include receiving or storing instructionsand/or data implemented in accordance with the foregoing descriptionupon a carrier medium. Suitable carrier mediums include storage mediumsor memory mediums such as magnetic or optical media, e.g., disk orCD-ROM, as well as signals such as electrical, electromagnetic, ordigital signals, conveyed via a communication medium such as networks202 and 204 and/or a wireless link.

Although the system and method of the present invention have beendescribed in connection with several embodiments, the invention is notintended to be limited to the specific forms set forth herein, but onthe contrary, it is intended to cover such alternatives, modifications,and equivalents as can be reasonably included within the spirit andscope of the invention as defined by the appended claims.

1-36. (canceled)
 37. A database management method comprising: collectingstatistics relating to operation of a database, the database comprisingone or more database objects, the statistics comprising activity-levelstatistics that measure a level of activity of the one or more databaseobjects; determining characteristics of the database objects;determining actions to be performed on the database objects based on thecharacteristics of the database objects; automatically determining aschedule for performing the actions on the database objects, wherein theschedule is based on the activity-level statistics; and performing theactions on the database objects based on the schedule.
 38. The databasemanagement method of claim 37, wherein the statistics compriseobject-level statistics.
 39. The database management method of claim 37,wherein the act of determining the characteristics of the databaseobjects comprises determining the characteristics of the databaseobjects using the collected statistics.
 40. The database managementmethod of claim 37, wherein the act of determining the characteristicsof the database objects comprises determining the characteristics of thedatabase objects using one or more policies.
 41. The database managementmethod of claim 40, further comprising allowing a user to customize theone or more policies.
 42. The database management method of claim 37,wherein the act of determining the characteristics of the databaseobjects comprises determining the characteristics of the databaseobjects using one or more definitions.
 43. The database managementmethod of claim 42, further comprising allowing a user to customize theone or more definitions.
 44. The database management method of claim 37,further comprising confirming the performing the actions on the databaseobjects.
 45. The database management method of claim 37, furthercomprising monitoring results of the performing the actions on thedatabase objects.
 46. The database management method of claim 45,further comprising analyzing the results of the performing the actionson the database objects.
 47. The database management method of claim 46,further comprising reconfiguring one or more policies based on theanalyzing the results of the performing the scheduled actions on thedatabase objects.
 48. The database management method of claim 37,wherein the act of determining the characteristics of the databaseobjects comprises automatically determining the characteristics of thedatabase objects.
 49. The database management method of claim 37,wherein the act of determining the actions to be performed on thedatabase objects based on the characteristics of the database objectscomprises automatically determining the actions to be performed on thedatabase objects based on the characteristics of the database objects.50. The database management method of claim 37, wherein the act ofperforming the actions on the database objects based on the schedulecomprises automatically performing the actions on the database objectsbased on the schedule.
 51. A carrier medium comprising programinstructions, wherein the program instructions are computer-executableto implement: collecting statistics relating to operation of a database,the database comprising one or more database objects, the statisticscomprising activity-level statistics that measure a level of activity ofthe one or more database objects; determining characteristics of thedatabase objects; determining actions to be performed on the databaseobjects based on the characteristics of the database objects;automatically determining a schedule for performing the actions on thedatabase objects, wherein the schedule is based on the activity-levelstatistics; and performing the actions on the database objects based onthe schedule.
 52. The carrier medium of claim 51, wherein the statisticscomprise object-level statistics.
 53. The carrier medium of claim 51,wherein the act of determining the characteristics of the databaseobjects comprises determining the characteristics of the databaseobjects using the collected statistics.
 54. The carrier medium of claim51, wherein the act of determining the characteristics of the databaseobjects comprises determining the characteristics of the databaseobjects using one or more policies.
 55. The carrier medium of claim 54,wherein the program instructions are further computer-executable toimplement customizing the one or more policies.
 56. The carrier mediumof claim 51, wherein the act of determining the characteristics of thedatabase objects comprises determining the characteristics of thedatabase objects using one or more definitions.
 57. The carrier mediumof claim 56, wherein the program instructions are furthercomputer-executable to implement customizing the one or moredefinitions.
 58. The carrier medium of claim 51, wherein the programinstructions are further computer-executable to implement confirming theperforming the actions on the database objects.
 59. The carrier mediumof claim 51, wherein the program instructions are furthercomputer-executable to implement monitoring results of the performingthe actions on the database objects.
 60. The carrier medium of claim 59,wherein the program instructions are further computer-executable toimplement analyzing the results of the performing the actions on thedatabase objects.
 61. The carrier medium of claim 60, wherein theprogram instructions are further computer-executable to implementreconfiguring one or more policies based on the analyzing the results ofthe performing the scheduled actions on the database objects.
 62. Thecarrier medium of claim 51, wherein the act of determining thecharacteristics of the database objects comprises automaticallydetermining the characteristics of the database objects.
 63. The carriermedium of claim 51, wherein the act of determining the actions to beperformed on the database objects based on the characteristics of thedatabase objects comprises automatically determining the actions to beperformed on the database objects based on the characteristics of thedatabase objects.
 64. The carrier medium of claim 51, wherein the act ofperforming the actions on the database objects based on the schedulecomprises automatically performing the actions on the database objectsbased on the schedule.
 65. A database management system comprising: aCPU; a database coupled to the CPU, wherein the database comprises oneor more database objects; a memory coupled to the CPU, wherein thememory stores program instructions which are executable by the CPU to:collect statistics relating to operation of the database, wherein thestatistics comprise activity-level statistics that measure a level ofactivity of the one or more database objects; determine characteristicsof the database objects; determine actions to be performed on thedatabase objects based on the characteristics of the database objects;automatically determine a schedule for performing the actions on thedatabase objects, wherein the schedule is based on the activity-levelstatistics; and perform the actions on the database objects based on theschedule.
 66. The database management system of claim 65, wherein thestatistics comprise object-level statistics.
 67. The database managementsystem of claim 65, wherein in the act of determining thecharacteristics of the database objects, the program instructions arefurther executable by the CPU to determine the characteristics of thedatabase objects using the collected statistics.
 68. The databasemanagement system of claim 65, wherein in the act of determining thecharacteristics of the database objects, the program instructions arefurther executable by the CPU to determine the characteristics of thedatabase objects using one or more policies.
 69. The database managementsystem of claim 68, wherein the program instructions are furtherexecutable by the CPU to customize the one or more policies.
 70. Thedatabase management system of claim 65, wherein in the act ofdetermining the characteristics of the database objects, the programinstructions are further executable by the CPU to determine thecharacteristics of the database objects using one or more definitions.71. The database management system of claim 70, wherein the programinstructions are further executable by the CPU to customize the one ormore definitions.
 72. The database management system of claim 65,wherein the program instructions are further executable by the CPU toconfirm the performing the actions on the database objects.
 73. Thedatabase management system of claim 65, wherein the program instructionsare further executable by the CPU to monitor results of the performingthe actions on the database objects.
 74. The database management systemof claim 73, wherein the program instructions are further executable bythe CPU to analyze the results of the performing the actions on thedatabase objects.
 75. The database management system of claim 74,wherein the program instructions are further executable by the CPU toreconfigure one or more policies based on analyzing the results of theperforming the scheduled actions on the database objects.
 76. Thedatabase management system of claim 65, wherein in the act ofdetermining the characteristics of the database objects, the programinstructions are further executable by the CPU to automaticallydetermine the characteristics of the database objects.
 77. The databasemanagement system of claim 65, wherein in the act of determining theactions to be performed on the database objects based on thecharacteristics of the database objects, the program instructions arefurther executable by the CPU to automatically determine the actions tobe performed on the database objects based on the characteristics of thedatabase objects.
 78. The database management system of claim 65,wherein in the act of performing the actions on the database objectsbased on the schedule, the program instructions are further executableby the CPU to automatically perform the actions on the database objectsbased on the schedule.